If you are new to the MPW environment or C, and/or have little experience with the concepts of makefiles and the building process, I refer you ( with a lump in my throat) to the MPW documentation that I hope you possess. In it you will learn about what the heck Dependency¬ 2.0 can do for you, and how you can better harness its power. In the meantime, drop the Tool in your MPW:Tools: folder, and try brushing up on some fundamental concepts.
In a nutshell, Dependency¬ 2.0 will examine your C source code file and look for #include <fileName> statements contained therein. When it finds an #include'd fileName, it will report to you that your target is dependent on this file to be decide when your target should be recompiled. If fileName is newer than your target, the your target needs recompilation. Dpenedency¬ 2.0 will then attempt to locate this fileName on your disk and repeat the process over and over again until no other files exist that your target #include's; whether directly, or thorough an #include' d file that #include'd another file, etc............ This process is tedious to ferret out by hand, and is frought with errors. That is the inspiration behind Dependency¬.
I wrote it because I needed it, and if you work on a C project, you need it too. To my knowledge nothing else exists that works as simply and easily as Dependency¬. Apple's MakeMake tool is pretty powerful, but contains a bewildering array of options needed to get it to work. I still haven't figured MakeMake out, but you may want to give it a look ( on APDA CD's ). The point is that you probably won't have to figure MakeMake out as long as you have Dependency¬ at your command.
Also, since the Version 1 release, I have received a lot of AppleLinks regarding its use and improvement. If you are among those who have taken the time to send a message regarding Dependency¬, I want to express my thanks, and hope that you will similarly respond to the new Version 2 incarnation.
If you are a new user, I hope Dependency¬ will save you the work it has saved myself and others. Please drop me a line so I can hear you suggestions, problems, criticisms, and improvements.
